Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: add gpt-tokenizer #251

Merged
merged 1 commit into from
Aug 18, 2024
Merged

feat: add gpt-tokenizer #251

merged 1 commit into from
Aug 18, 2024

Conversation

arvinxx
Copy link
Contributor

@arvinxx arvinxx commented Aug 17, 2024

gpt-tokenizer : https://github.com/niieani/gpt-tokenizer

this package can count token in browser : https://gpt-tokenizer.dev/

but the cost is the large file size.

Summary by CodeRabbit

  • New Features
    • Added support for a new tokenizer library, enhancing the project's capabilities.
  • Chores
    • Updated dependency management by including "gpt-tokenizer" in the project.

Copy link

coderabbitai bot commented Aug 17, 2024

Walkthrough

The recent update to the project involves adding a new dependency, "gpt-tokenizer," to the package.json file. This enhancement allows the project to utilize a tokenizer library without modifying any existing functionality. The inclusion of this library expands the project's capabilities, promoting better dependency management while maintaining the integrity of the current codebase.

Changes

Files Change Summary
package.json Added new dependency "gpt-tokenizer": { "version": "*" }

Poem

🐇 In the garden of code, a new friend appears,
A tokenizer swift, bringing joy and no fears.
With every new line, our functions will dance,
Embracing the change, let’s give it a chance!
Hops of delight, in our project we play,
For growth and for fun, let’s code night and day! 🌼


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 99e09ae and 819ae40.

Files selected for processing (1)
  • package.json (1 hunks)
Files skipped from review due to trivial changes (1)
  • package.json

@afc163 afc163 enabled auto-merge (squash) August 18, 2024 02:15
@afc163 afc163 merged commit d76d145 into cnpm:master Aug 18, 2024
4 checks passed
fengmk2 pushed a commit that referenced this pull request Aug 18, 2024
[skip ci]

## [1.113.0](v1.112.0...v1.113.0) (2024-08-18)

### Features

* add gpt-tokenizer ([#251](#251)) ([d76d145](d76d145))
* add speedtouch ([#248](#248)) ([99e09ae](99e09ae))
@arvinxx arvinxx deleted the patch-1 branch December 14, 2024 02:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants